I have created a module attribute called Revision History, and inserted a Word document with the revision history table in it. The insert OLE object menu item isn't available when editing a module attribute, just the properties window. So I dragged the Word document into the text window of the attribute, and then changed the OLE properties to "display an editable view". All that seems to be working ok, however, when I grab this table in RPE (via Module/Attribute/Revision History) into a text element, I am only getting a "picture" of the table, not the table. I have set the specification property in the launcher to preserve OLE objects, and in fact all other embedded OLEs as Word documents in Objects render just fine. Anyone have any insight into what's different about the module attribute? I'm guessing this isn't done much, and may be a gap in the handling of OLEs. cliff.sadler - Wed Jun 26 10:48:58 EDT 2013 |
Re: Embedded OLE objects in Module Attributes I think this is an issue with RPE not DOORS, the rtf in module attributes seems to be handled by DOORS in the same way as for object attributes (make sure you are using a text attribute not a string). The company word exporter uses a text module attribute to hold change control data in a word ole much like yours and it works fine. Note that the best way to get ole's into a module attribute is to copy the table inside word, then do a "paste special" into itself as a embedded document then cut and paste the embedded document direct into the text module attribute if that makes sense, thats the way I have always done it anyway. |
Re: Embedded OLE objects in Module Attributes Richard_Good - Wed Jun 26 13:16:21 EDT 2013 I think this is an issue with RPE not DOORS, the rtf in module attributes seems to be handled by DOORS in the same way as for object attributes (make sure you are using a text attribute not a string). The company word exporter uses a text module attribute to hold change control data in a word ole much like yours and it works fine. Note that the best way to get ole's into a module attribute is to copy the table inside word, then do a "paste special" into itself as a embedded document then cut and paste the embedded document direct into the text module attribute if that makes sense, thats the way I have always done it anyway. If I'm not mistaken, it's a setting in RPE Launcher, under Runtime->Metadata properties, "OLEs as static images". Set this to false and you'll get the OLE as it should be. However, note that this is a global setting, so all OLEs will now be set not to be static images. /sekrbo
|